Unify command recognition for PhysicalDevice and DebugPort - #73

Replace manual if/elif byte-parsing in debug ports with a table-driven
approach: declare command entries (binary or text) and implement only
device logic in process_command(). Migrate Sutter's DebugSerialPort,
create Intellidrive's missing DebugSerialPort, and add 12 new tests.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…ck sides

Add matches(), extractParams(), formatResponse() to Command/TextCommand/DataCommand
so the same objects define both the client protocol and debug port recognition.
Remove BinaryCommandEntry/TextCommandEntry dataclasses from debugport.py, replacing
them with a single polymorphic loop over Command objects in TableDrivenDebugPort.
Update SutterDevice and IntellidriveDevice to use class-level commands dicts.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

TextCommand.extractParams() now returns a dict when the matchPattern uses
named groups (?P<name>...), and formatResponse() accepts dicts for named
template parameters. Anonymous groups and positional tuples still work.

Add class and method docstrings to TableDrivenDebugPort with examples
showing named parameters for self-documenting command definitions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Use (?P<register>...), (?P<value>...), (?P<mode>...) in matchPatterns
and {register}, {value}, {mode} in text/responseTemplate fields.
process_command now uses params["register"] instead of params[0].

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Add requestFields and responseFields to DataCommand, mapping struct
fields to names so extractParams returns a dict and formatResponse
accepts a dict. Sutter process_command now uses params['x'], params['y'],
params['z'] and returns {'header': ..., 'x': ..., 'y': ..., 'z': ...,
'terminator': ...}.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Document the module, all four classes (Command, TextCommand,
MultilineTextCommand, DataCommand), and their key methods. Covers
both the send side and recognition side roles, with parameter
descriptions and examples.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Every PhysicalDevice defines a commands dict that serves both sides:
sending commands to real hardware and creating mock debug ports that
receive those same commands and reply in the correct format.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

The parameter is a format string, not plain text. Rename it everywhere:
TextCommand/MultilineTextCommand __init__, all self.text references,
all call sites across device classes, debug ports, and tests.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

The project's test files follow a 'testFooBar.py' naming convention
(no underscore separator). Pytest's default 'python_files' pattern
is 'test_*.py', so 'pytest hardwarelibrary/tests/' returned zero
collected tests -- tests could only be run by naming files
explicitly. That had become a real friction now that the suite
crosses 500 tests.

Added a [tool.pytest.ini_options] section to pyproject.toml:

- testpaths = ["hardwarelibrary/tests"]  -- so plain 'pytest' works
- python_files = ["test*.py"]            -- match the project's naming
- norecursedirs = ["deprecated"]         -- skip unmaintained legacy
                                            tests that error on import

After this, 'pytest' from the repo root collects 476 tests and
reports 263 passed, 213 skipped (hardware-gated), 0 failures.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Replaces the ad-hoc CoboltDebugSerial class with a nested
DebugSerialPort(TableDrivenDebugPort) inside CoboltDevice, and
moves the protocol definition into a class-level 'commands' dict.

Eleven commands captured: GET_POWER, GET_REQUESTED_POWER, SET_POWER,
GET_ON_OFF, TURN_ON, TURN_OFF, GET_SERIAL_NUMBER, TURN_AUTOSTART_ON,
TURN_AUTOSTART_OFF, GET_AUTOSTART, GET_INTERLOCK. Each is declared
once with text_format/replyPattern (for the device send-side) plus
matchPattern/responseTemplate (for the debug port to recognize and
respond).

The doX methods now use commands["NAME"].send(port=self.port) and
read .matchGroups for the parsed values, eliminating the parallel
hand-rolled regex dispatch that lived in CoboltDebugSerial.write
(~120 lines of inline pattern matching).

The DebugSerialPort holds the mock device state (power, isOn,
autostart, serialNumber, interlock) and process_command returns
either a dict (for templated responses) or a raw "OK\r\n" / error
string. The background power-ramp thread (increasePowerSlowlyInBackground)
is preserved.

Manual sanity check: end-to-end roundtrip works via
CoboltDevice(bsdPath='debug') -- initializeDevice succeeds, all
queries return sensible values, doSetPower(0.5) converges through
the background ramp.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

DebugEchoPort was a no-op subclass of DebugPort with an empty
__init__ that just called super(). It existed as a named alias for
"DebugPort used for echo testing", but added no behavior -- the
echo logic lives in DebugPort.processInputBuffers.

Removed:
- hardwarelibrary/communication/echoport.py (the alias)
- DebugEchoPort export from hardwarelibrary/communication/__init__.py
- TestDebugEchoPort class in testCommunicationPorts.py (was a
  duplicate of TestDebugPortDefaultsToECho, with the only
  difference being which alias it instantiated)

Updated:
- TestSlowDebugEchoPort now instantiates DebugPort() directly
  instead of DebugEchoPort(). Same behavior; one less indirection.

Tests still pass (246 passed, 202 skipped on the full suite).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>